About Meter Triggers
Section titled “About Meter Triggers”In UniCMMS, Meter triggers automate actions based on real readings from your Meters module. They watch the numeric data technicians record; when a reading meets the rule you defined, the trigger fires immediately (or as configured in your automation), without waiting for a calendar date.
Example: You define a meter trigger: “reading exceeds 15,000 kWh.” After you link it to active automation, the system runs the linked action as soon as a recorded reading reaches that threshold.
Meter triggers assume you use meters to track consumption or usage (hours, cycles, energy, etc.). For calendar-only scheduling, use Time triggers. For an overview of both types, see About Triggers.
When to use meter triggers
Section titled “When to use meter triggers”Use a meter trigger when the right moment depends on how much has been used or produced, for example:
- Preventive maintenance every N operating hours or N kWh
- Alarms or workflows when consumption crosses a limit
- Usage-based follow-up instead of fixed calendar dates
Meter trigger condition logic
Section titled “Meter trigger condition logic”UniCMMS evaluates incoming meter readings against the conditions below. Understand the Reset requirement so the system does not fire duplicate actions for a single event. (The same reference table also appears on About Triggers.)
| Condition | System logic | Reset requirement |
|---|---|---|
| is above | Executes when the entered reading is higher than the set threshold. | Yes: the reading must drop below the threshold before it can trigger again. |
| is below | Executes when the entered reading is lower than the set threshold. | Yes: the reading must rise above the threshold before it can trigger again. |
| is equal to | Executes every time the entered reading is exactly equal to the set threshold. | No: triggers on every exact match. |
| increases by | Executes every time the total meter reading increases by the set threshold value. | No: continuous interval from the last trigger point. |
| decreases by | Executes every time the total meter reading decreases by the set threshold value. | No: continuous interval from the last trigger point. |
| increases by (spike model) | Executes when the difference between the last reading and the one before it increases by the set value. | No: each new reading is evaluated against the reading immediately before it. |
| decreases by (spike model) | Executes when the difference between the last reading and the one before it decreases by the set value. | No: each new reading is evaluated against the reading immediately before it. |
Important: Meter triggers react to readings recorded in the Meters module. They do not replace asset runtime counters unless those values are kept in meter history.
Permissions
Section titled “Permissions”Viewing meter triggers requires View meter triggers. Creating or changing them requires the appropriate Add, Edit, and Delete meter trigger permissions where your tenant enables them.
Related topics
Section titled “Related topics”- About Triggers — triggers module overview
- How to Create a Meter Trigger
- About Time Triggers
- Meters how-tos under Maintenance → Meters (create meters, record readings)